Protocol gateway between an h.323 terminal and another terminal, without master role implementation

ABSTRACT

A protocol gateway for setting up multimedia sessions between a first terminal, using a first protocol (for example H.323), and a second terminal, using a second protocol, said first protocol requiring the determination of a master, which protocol gateway is characterized in that it has available to it means for forcing said first terminal to assume the role of master.

[0001] The present invention relates to telecommunication networks, and more specifically, it concerns the management of multimedia sessions set up on top of a data network. This data network may be compliant with the TCP/IP (Transmission Control Protocol/Internet Protocol) family of protocols, and it may in particular be the Internet.

[0002] Hereinafter, “multimedia session” refers to the transmission of data between two or more terminals involving several media types, in particular, most often voice and/or video. These multimedia sessions are commonly called VoIP for Voice over IP (Internet Protocol).

[0003] Prior to setting up the actual multimedia session, the terminals involved must exchange information in order to, in particular, set certain parameters of the multimedia session.

[0004] These parameters relate, for example, to characteristics of the medium (voice encoding format, video format, etc.). These characteristics may be determined according to the capabilities of the terminals participating in the multimedia session.

[0005] This setup phase of the multimedia session takes place in accordance with a particular protocol.

[0006] However, these protocols are quite varied. In particular, mention may be made of the H.323 protocol defined by the ITU-T (International Telecommunication Union Telecommunication Standardization Sector) and the SIP (Session Initiation Protocol) defined by RFC 2543 (Request For Comments) of the IETF (Internet Engineering Task Force).

[0007] With the aim, in particular, of hiding these differences and enabling terminals using different protocols to coexist, as is known from the prior art, protocol gateways can be placed between the various terminals.

[0008] Typically, these protocol gateways form part of call centers or controllers.

[0009]FIG. 1 schematically illustrates an example of setting up a multimedia session between two telecommunication terminals.

[0010] Terminal T_(A) is the initiator of the multimedia session. It therefore initiates a multimedia session setup negotiation m_(A) with the call center CC that has a protocol gateway. This multimedia session setup negotiation contains, in particular, information on the media characteristics which terminal T_(A) can handle (video format, voice encoding type, etc.) and is compliant with the H.323 protocol.

[0011] The call center CC then negotiates with the recipient of the multimedia session, that is terminal T_(B), by exchanging messages m_(B) according to the SIP protocol, and then it sets up the multimedia session MS between the two terminals T_(A) and T_(B).

[0012] If necessary, if the two terminals cannot agree upon media characteristics to communicate (for example, they do not support any common video encoding format), the call center may set up the multimedia session using a media gateway.

[0013] However, there is a problem if one of the two terminals uses the H.323 protocol and the other terminal (or the other terminals in the case of a multimedia session between more than two participants) uses a protocol other than H.323 (for example, the SIP protocol).

[0014] This is because the H.323 protocol includes a phase to determine a “master” terminal and a “slave” terminal. The protocol assumes that each terminal can take on either role. The determination depends on a classification, established beforehand, of various types of terminal: the most powerful terminal takes on the role of “master” and for equal power, an arbitrary choice is made to determine which of the two terminals will assume the role of master.

[0015] This role of master is taken into account in the event of conflicts or problems. It involves a significant degree of complexity in the terminal implementing it.

[0016] In the case in which a multimedia session is set up via a protocol gateway and in which only one terminal uses the H.323 protocol, a problem arises since the phase for determining the “master” and “slave” roles can take place only between the terminal using the H.323 protocol and the protocol gateway.

[0017] Referring again to the example of FIG. 1, this means that the determination of the “master” and “slave” roles must take place between terminal T_(A) and the call center CC containing the protocol gateway.

[0018] In accordance with the H.323 protocol, this mechanism therefore assumes that the protocol gateway can take on the role of “master”. The gateway must therefore support all the protocol and software mechanisms inherent to this function.

[0019] Since these mechanisms are complex, this type of solution involves an increase in processing resources required to enable the protocol gateway to function (memory resources, CPU (Central Processing Unit), etc.).

[0020] Moreover, since this protocol gateway is typically included in a call center, this use of resources can be to the detriment of other functions in the call center.

[0021] Furthermore, the architecture of Internet type data networks involves, generally, minimizing the processing resources required within the network, since the lifetime of the hardware within the network is assumed to be greater than that of the terminals and any increase in resources required and any update is expensive and to be avoided.

[0022] Thus, in Internet type networks, a large part of the intelligence is transferred to the terminals.

[0023] The result of this is that the increase in complexity of the protocol gateway is a major drawback.

[0024] The aim of the present invention is to propose a protocol gateway for setting up multimedia sessions between a terminal using the H.323 protocol and a terminal using another protocol, but not requiring implementation of the role of “master”.

[0025] To achieve this, a first subject of the invention is such a protocol gateway for setting up multimedia sessions between a first terminal, using a first protocol (for example the ITU-T H.323 protocol), and a second terminal, using a second protocol, the first protocol requiring determination of a master. This protocol gateway is characterized in that it has available to it means for forcing the first terminal to assume the role of master.

[0026] Another subject of the invention is a call center including such a protocol gateway.

[0027] Another subject of the invention is a process for setting up a multimedia session between a first terminal using a first protocol (for example the ITU-T H.323 protocol), and a second terminal, using a second protocol, the first protocol requiring determination of a master, the first and second terminals communicating by means of a protocol gateway. This process is characterized in that it includes steps of:

[0028] sending of a message to determine the Master/Slave status.

[0029] sending of a response message by the protocol gateway, containing a field forcing the first terminal to assume the role of master.

[0030] The invention, its features and its advantages will become more clearly apparent in the description below of an implementation given with reference to the attached figures.

[0031]FIG. 1, already referred to, schematically illustrates the setting up of a multimedia session between two terminals.

[0032]FIG. 2 illustrates the phase for determining the role of master between a terminal and a protocol gateway.

[0033] In the example of FIG. 2, the call center CC includes a protocol gateway G. The purpose of this protocol gateway is to allow multimedia sessions to be set up between terminals that do not use the same protocol.

[0034] Terminal T_(A) uses the H.323 protocol. This terminal wants to set up a multimedia session with one or more other terminals, not depicted in the figure, which use protocols other than H.323. As mentioned previously, the SIP protocol may feature here.

[0035] First, terminal T_(A) transmits to the protocol gateway G a message m₁ for determining the Master/Slave status.

[0036] In accordance with the H.323 protocol, this message is a “MasterSlaveDetermination”. It contains as a parameter, first the terminal type terminalType, and secondly a random number, statusDeterminationNumber.

[0037] As indicated in section 6.2.8.4 of ITU-T Recommendation H.323, the terminal type is a number that is representative of its processing power.

[0038] In the prior art, the processing power is used to determine which party in a multimedia session should be chosen as master.

[0039] The random number statusDeterminationNumber is used as the means of arbitration when both parties are of equal power.

[0040] In accordance with the invention, the protocol gateway G responds to the message m₁ by transmitting a message m₂. This message m₂ is a “MasterSlaveDeterminationAck” message.

[0041] Regardless of the processing power and the random number indicated in the message m₁, the protocol gateway G decides to take on the role of slave, forcing the terminal T_(A) to assume the role of master.

[0042] To this end, the gateway sets the “Decision” parameter, as defined in ITU-T Recommendation H.245, to the value “Master”.

[0043] On receiving this message m₂, terminal T_(A) may respond with a message m₃. This message m₃ is also a “MasterSlaveDeterminationAck” message. This time, the parameter XXX contains the value “Slave”, indicating that terminal T_(A) accepts that the protocol gateway G takes on the role of slave.

[0044] Thus, the protocol gateway G is freed from management of the role of master, while terminal T_(A) is unaffected. For terminal T_(A), everything takes place as a normal dialog with another terminal.

[0045] Furthermore, it should be noted that in accordance with Recommendation H.323, the terminals must implement management of the role of master, such that the mechanism of the invention does not have any additional constraint on these terminals. 

1. A protocol gateway for setting up multimedia sessions between a first terminal, using a first protocol, and a second terminal, using a second protocol, said first protocol requiring determination of a master, which protocol gateway is characterized in that it has available to it means for forcing said first terminal to assume the role of master.
 2. The protocol gateway as claimed in claim 1, in which said first protocol is the ITU-T H.323 protocol.
 3. The protocol gateway as claimed in claim 2, in which said means are able to return a “MasterSlaveDeterminationAck” message in response to a “MasterSlaveDetermination” message, containing a “Decision” field set to “Master”.
 4. The protocol gateway as claimed in any of the preceding claims, in which said second protocol is the SIP protocol.
 5. A call center, characterized in that it includes a protocol gateway in accordance with any of the preceding claims.
 6. A process for setting up a multimedia session between a first terminal using a first protocol and a second terminal using a second protocol, said first protocol requiring the determination of a master, said first and second terminals communicating by means of a protocol gateway, which process is characterized in that it includes steps of: sending of a message m₁ to determine the master/slave status, sending of a response message m₂ by said protocol gateway, containing a field forcing said first terminal to assume the role of master.
 7. The process as claimed in the preceding claim, in which said first protocol is the ITU-T H.323 protocol.
 8. The process as claimed in the preceding claim, in which said response message is a “MasterSlaveDeterminationAck” message containing a “Decision” field set to “Master”. 